Update FIH tests to use recent TFM and bump toolchain to 14.2 to ensure compatibility with the TFM version #2426
Conversation
maulik-arm
commented
Aug 12, 2025
maulik-arm
commented
- Update FIH tests to reference and work with the recent Trusted Firmware-M (TFM) version.
- Update Docker image to use toolchain version 14.2 for compatibility.
- Fix compatibility issues encountered with new TFM/toolchain.
- Update FIH tests to reference and work with the recent Trusted Firmware-M (TFM) version. - Update Docker image to use toolchain version 14.2 for compatibility. - Fix compatibility issues encountered with new TFM/toolchain. Signed-off-by: Maulik Patel <[email protected]> Change-Id: Ibc9234cb6932ba8e7beb5ce8e0591c4ab91dbecb
|
|
||
| # Function to update/install ARM Embedded GCC inside the Docker container | ||
| update_cross_gcc() { | ||
| ARM_GCC_URL="https://developer.arm.com/-/media/Files/downloads/gnu/14.2.rel1/binrel/arm-gnu-toolchain-14.2.rel1-x86_64-arm-none-eabi.tar.xz" |
There was a problem hiding this comment.
why can this package not be got from the distro itself? How long will this file be available? How often can it be accessed per IP? Is it rate limited? I don't think we should be putting things like this in given that there's so many unknown variables and given that we've seen countless problems in the past trying to get even the tfm repo for CI checks
There was a problem hiding this comment.
You are right, the package has to be from the distro (which means I have to update the distro). But how do I do that? Did you missed the discord conversation where I raised the same question? https://discord.com/channels/1106321706588577904/1390625171785646151. let me know how to update the distro and I will do the rest.
There was a problem hiding this comment.
In that from @d3zd3z :
I think the correct solution here is to figure out how to get the mcuboot docker images to be properly owned by trustedfirmware.org. I don't know if that moves us into a scenario where they are going to charge for this, though.
I see no comment suggesting that packages should be manually added like this, action is on @d3zd3z to deal with docket image ownership
